home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19941221-19950208
/
000457_news@columbia.edu_Tue Feb 7 07:55:35 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-07-31
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA10274
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Wed, 8 Feb 1995 00:12:19 -0500
Received: by apakabar.cc.columbia.edu id AA10836
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Wed, 8 Feb 1995 00:12:18 -0500
Path: news.columbia.edu!panix!news.mathworks.com!udel!gatech!swrinde!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit TSR for background xfers?
Message-Id: <1995Feb7.135535.40928@cc.usu.edu>
Date: 7 Feb 95 13:55:35 MDT
References: <3go00i$bie@crl12.crl.com> <1995Feb1.100246.40094@cc.usu.edu> <3h5mj8$kar@Mercury.mcs.com> <1995Feb6.134931.40786@cc.usu.edu> <3h8611$eif@Mars.mcs.com>
Organization: Utah State University
Lines: 42
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <3h8611$eif@Mars.mcs.com>, les@MCS.COM (Leslie Mikesell) writes:
> In article <1995Feb6.134931.40786@cc.usu.edu>,
> Joe Doupnik <jrd@cc.usu.edu> wrote:
>
>>> I'm running a DOS program called ACCESS PLUS that is intended to be used
>>> with the attmail service that uses a 60K TSR to provide scheduled calls
>>> in the background. It is running on many machines without causing too
>>> much trouble from being a TSR, so it is at least possible. It appears
>>> to run an xmodem-like protocol modified so that the total packet size
>>> is 256 bytes, and has a minimal scripting language for dialing and
>>> login. However, there are things I don't like about the rest of
>>> this package. I'd like to replace it with something that does MIME
>>> attachments without losing the ability to do the background communication.
<omitting much>
>> I disagree here. The market is for the big scale product, not
>>a tailor-made component. There is no interest at this end in becoming
>>a parts supplier for free.
>
> I don't mean to imply that you have any obligation to provide such
> a thing for free, but I still think there is a need for it and it
> fits into the kermit model of making everything talk to everything
> else on the cheap. The other components needed to put a workable
> system together are available in various free or low-cost shareware
> forms that could be glued together to build a custom system. For
> example you could use uqwk on a unix host and any of several qwk/soup
> readers, or set up something similar as a custom gateway for Pegasus.
> The critical points to making it usable are that the end points
> appear as users on the host machine rather than remote machines,
> and that the communications must take care of itself with scheduled
> calls in the background as an option.
>
> But maybe it's too late for simple serial communications.
----------------
I think the time passed in the early 70's when Unix grew up,
even though there is a modern resurgence this year as "service providers"
appear in every other garage to guide folks to the ISH.
There is always a need for someone(s) to make working systems from
components. However, the Kermit designers may not be interested in spending
their own time and effort in such work (they too, like everyone, have plans
and goals). Hence a contractural arrangement would be needed to create the
group to do the special job.
Joe D.